   File transfers...
 
   The designers of Citadel saw downloading as just another form of reading
information from the BBS, hence the file transfer commands are included among
the .R(ead) extended commands.  A later enhancement created a "standard"
syntax for file transfers: .R(ead) [Protocol] F(ile), allowing more protocols
to be implemented as they appear.  Currently you have these options:
 
  .RF   .R(ead) F(ile)   no protocol, just raw data, which becomes a bit messy
if you try to read a binary file like an ARChive.
  .RTF  .R(ead) T(ext) F(ile)  a pseudo-protocol, T(ext) will format the file
to your screen width, just like the messages.
  .RXF  .R(ead) X(modem) F(ile)  the old standby, Xmodem
protocol, which should be used for binary files or noisy connections.
  .RYF  .R(ead) Y(modem) F(ile)  This is NOT* Ymodem batch, but Ymodem single
file transfer.
  .RWF  .R(ead) W(xmodem) F(ile)  Windowed Xmodem -- very fast for
packet-switched networks.
  .RVF  .R(ead) V(anilla) F(ile)  Pseudo-ascii transfer.  It's just a straight
ascii transfer terminated by 2 CAN (ctrl-X)  characters.  When uploading, you
MUST* terminate the transfer with 2 CAN characters to have the BBS accept the
upload.

  If you are downloading more than one file, you may use Ymodem BATCH mode to
download them.

  .RXB  .R(ead) X(modem) B(atch-mode file)  Ymodem batch download with 128
byte blocks only.
  .RYB  .R(ead) Y(modem) B(atch-mode file)  Normal Ymodem batch download.
 
  Uploading uses the same options. (.E(nter) [Protocol] F(ile))  If you do a
.E(nter) F(ile), the BBS will assume that you intend to do a XMODEM upload.
STadel does not allow Ymodem batch mode uploads.
 
  SEE ALSO:
%FILES	General information on uploading/downloading files.
